Skip to main content
Version: 2.0

Flow Efficiency

For years, engineering teams have fixated on velocity – the amount of work completed in a sprint. It's a useful metric, sure, but it often paints an incomplete, even misleading, picture. A team can achieve high velocity while simultaneously being deeply frustrated, constantly context-switching, and churning through unplanned work. That's where Flow Efficiency comes in. It’s about measuring not just how much work gets done, but how smoothly it gets done.

As an engineering leader with two decades under my belt, I've seen teams prioritize speed at the expense of sanity. The result? Burnout, technical debt, and ultimately, slower delivery in the long run. Flow Efficiency offers a way to diagnose and address those underlying friction points.

Have you experienced the frustration of a high-velocity team burning out, delivering late, or producing work that doesn’t quite meet customer needs? This is often a symptom of ignoring the flow of work – and where Flow Efficiency can help.

What Is Flow Efficiency?​

Flow Efficiency, popularized by the Value Stream Management (VSM) movement – a methodology focused on analyzing and optimizing the steps involved in delivering value to the customer – is a measure of the percentage of time work spends actually being worked on, versus time spent in queues, handoffs, or blocked. It's calculated as:

Flow Efficiency = (Active Time / Total Lead Time) x 100

  • Active Time: The time developers are actively coding, testing, or directly contributing to the work.
  • Total Lead Time: The total time from when a work item is requested (e.g., a feature request, bug report) until it's delivered to the customer.

A high Flow Efficiency (ideally 80% or greater) indicates a streamlined process with minimal waste. A low number signals bottlenecks and friction. It's important to note that Flow Efficiency isn’t about pushing people to work faster; it’s about making it easier for them to work effectively.

Why is Flow Efficiency More Valuable Than Just Velocity?​

Let's illustrate with a simple example. Two teams both have a velocity of 40 story points per sprint.

  • Team A: Spends 70% of their time actively working on stories, the rest waiting on code review, dealing with unclear requirements, or unblocking dependencies. Their lead time for a typical story is 10 days. Flow Efficiency = (7 days / 10 days) x 100 = 70%
  • Team B: Spends 90% of their time actively working. Clear requirements, automated testing, and a robust CI/CD pipeline keep things moving. Their lead time is 7 days. Flow Efficiency = (6.3 days / 7 days) x 100 = 90%

Both teams have the same velocity, but Team B is delivering value much faster and with less frustration. They are more responsive to change and can iterate more quickly.

How to Measure and Improve Flow Efficiency​

Here’s a practical approach:

  1. Visualize Your Workflow: Use a Kanban board (physical or digital – Jira, Trello, Linear are good options) to map out the stages of your development process. This provides transparency into where work gets stuck.
  2. Track Lead Time & Cycle Time: These are crucial metrics.
    • Lead Time: From request to delivery (as defined above).
    • Cycle Time: The time spent actively working on the item.
  3. Identify Bottlenecks: Analyze your Kanban board and data. Where are items piling up? Common culprits:
    • Code Review: Long review times are a huge drag. Encourage smaller, more frequent reviews.
    • Dependency Hell: External dependencies or blocked tasks can halt progress. Prioritize unblocking efforts.
    • Unclear Requirements: Ambiguous or incomplete requirements lead to rework. Invest in proper specification and collaboration with product teams.
    • Context Switching: Frequent interruptions and shifting priorities kill productivity. Protect developer focus.
  4. Implement Solutions:
    • Automate Testing: Automated tests reduce manual effort and accelerate the feedback loop.
    • Improve Code Review Process: Tools like Crucible or Reviewable can streamline reviews. Set SLAs for review turnaround.
    • Break Down Work: Large tasks create bottlenecks. Decompose them into smaller, manageable chunks.
    • Invest in CI/CD: Automated build, test, and deployment pipelines accelerate delivery.
  5. Use Flow Metrics Tools: Consider tools like Jellyfish or Waydev which are purpose built for analyzing flow metrics.

Beyond the Numbers: A Culture of Flow​

Ultimately, Flow Efficiency isn’t just about metrics. It’s about fostering a culture of continuous improvement and empowering your team to deliver value with less friction. It requires psychological safety, open communication, and a proactive approach to obstacle removal.

I recall one team I worked with initially resistant to focusing on flow, accustomed to solely chasing velocity. After visualizing their workflow and realizing the sheer amount of time spent waiting, they were motivated to proactively address bottlenecks. The result was not only a significant increase in Flow Efficiency, but also a noticeable improvement in team morale.

Shifting focus from velocity can feel counterintuitive, but the long-term benefits – reduced burnout, increased predictability, and faster delivery – outweigh the initial adjustments.

By shifting your focus from how much work you’re completing to how smoothly it’s flowing, you can unlock a new level of productivity, reduce burnout, and deliver exceptional value to your customers.